I don't understand why liquid-fixpoint of version 8.10.7 (deprecated on Hackage and long outdated) is picked up by the CI script. Can someone help, please?

I don't understand why liquid-fixpoint of version 8.10.7 (deprecated on Hackage and long outdated) is picked up by the CI script. Can someone help, please?

Okay, I specified an exact version of liquid-fixpoint and that did the trick: CI is green now. It's not too bad (and liquidhaskell works with that single version only anyway), but I'd be curious to know why check.sh picked an ancient version of the library when I did not specify a version, if someone has energy to explain me.

Thanks for this, merging!

I don't understand why liquid-fixpoint of version 8.10.7 (deprecated on Hackage and long outdated) is picked up by the CI script. Can someone help, please?

Okay, I specified an exact version of liquid-fixpoint and that did the trick: CI is green now. It's not too bad (and liquidhaskell works with that single version only anyway), but I'd be curious to know why check.sh picked an ancient version of the library when I did not specify a version, if someone has energy to explain me.

I am not sure either, sounds a bit strange indeed - perhaps we can relax it later, dunno

Ah, I wasn't fully paying attention - I know it is a bit confusing but curator just ignores (or rather is unaware of) deprecations... see commercialhaskell/curator#46

So for Stackage we simply need to hardcode liquid-fixpoint < 8.10.7 - at least until this is fixed someday.
It only affects a handful of packages anyway.

I wonder if we could get liquidhaskell into LTS too...

So for Stackage we simply need to hardcode liquid-fixpoint < 8.10.7

Oh my, I didn't realize 8.10.7 doesn't have the leading zero, so it's the latest version. It all makes sense now.

Curator not accounting for depreciation isn't surprising at all: depreciation is a strange concept which we discuss on the cabal tracker a lot, and I believe it has spotting support across the whole ecosystem including cabal itself.

I wonder if we could get liquidhaskell into LTS too...

Yes, I'll submit a patch shortly (hopefully, over the weekend). Thank you!

@juhp how do I add it to an LTS exactly? I assumed it's opening an analogous PR against an lts* branch (e.g. lts24). But on Matrix I got a conflicting reply: something about other repositories...

Thank you for fixing the test suite problems btw: I could have done it myself.

No worries

Yes, we need to edit https://github.com/commercialhaskell/lts-haskell/blob/master/build-constraints/lts-24-build-constraints.yaml

Good idea to try building it locally first: stack --resolver lts build liquidhaskell liquid-fixpoint ...
(Also unfortunately the CI is not working there either currently.)